Non-linear program planner, preparation, and delivery system

ABSTRACT

The non-linear program planner, preparation, and delivery system performs multiplatform planning and scheduling across multiple content delivery platforms. The system coordinates planning to deliver high-quality video content in a very efficient and scalable manner. The system includes automated avails and other processes that increases the accuracy of the information provided to distribution partners. The system checks on content rights and incorporates metadata structures that facilitate delivery of content to a wide range of distribution channels. The invention increases accuracy, timeliness, and efficiency of content delivered to partners and allows providers to generate revenue from online (non-linear) platforms and over the top (OTT) video services.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority of U.S. ProvisionalApplication No. 62/352,053, filed on Jun. 20, 2016. This applicationincorporates by reference the entire contents of U.S. ProvisionalApplication No. 62/352,053, filed on Jun. 20, 2016.

TECHNICAL FIELD

This technology relates to media asset management. More specifically,the technology relates to planning, preparing, and delivering non-linearvideo content to distribution partners for viewing on digital mediaplayers across many platforms.

BACKGROUND

Media content providers have a growing business of nonlinear videodistribution. This demand is driven by the changing media consumptionsof viewers. About 10 years ago, the only video distributed outside ofthe linear broadcast was Video on Demand (VOD) services provided by somemulti-channel video programming distributors (MVPDs).

With the proliferation of devices, mobile operating systems and fastchanging viewing patterns, the MVPDs have expanded the VOD content tomeet this viewer demand. Providers now put VOD on traditionalset-top-boxes (STBs) and also on their browser and mobile sites andapplications. A product example of this is the TV-Everywhere productwhere the best content on cable television is available to consumers ofpay-TV via authenticated login across many devices and platforms.

As viewers shift to these other platforms, consumption of pay TVprograms have declined. Content creators have had to adapt from creatingcompelling linear content that can move audiences and win ratings toproviding that compelling content whenever and wherever audiences wantto consume it and in technical formats that best suit the growing numberof distribution platforms. Similarly, revenue from traditional Pay TVadvertisements has also declined. In response, content creators,distributors, and advertisers investigate different avenues to recoup adsales revenue as consumers watch video content on a variety of onlineplatforms (e.g., mobile, desktop, connected TV devices, online stores,transactional Video On Demand, electronic-sell-through, and the like).

SUMMARY

The system of the claimed invention allows video content providers toplan, prepare, and delivery video content to a wide range ofdistribution partners. The non-linear program planner, preparation, anddelivery system allows content providers to perform multiplatformplanning and scheduling across multiple content delivery platforms,including a variety of desktop and mobile computing devices, hardwarearchitectures, and operating systems. The system orchestrates end-to-endplanning to deliver high-quality video content by automaticallyperforming key portions of the processes in parallel to maximizeefficiency. The system includes automated partner content avails andother processes that increases the accuracy of the information providedto distribution partners. The system checks on content rights andincorporates metadata structures that facilitate delivery of content toa wide range of distribution channels. The invention increases accuracy,timeliness, and efficiency of content delivered to partners (e.g.,Google, Comcast, Apple, Netflix, etc.) and allows providers to generaterevenue from online (non-linear) platforms. This invention also allowsfor the content planning, preparation and delivery to support OTT (overthe top) video services.

The invention includes a non-linear video asset program planning,preparation, and delivery system. One example system includes anon-linear planning subsystem that receives a linear broadcast schedulefrom a linear schedule service system, receives content rights from acontent rights system, and receives a source video asset from a storagedevice. The linear broadcast schedule can include an air date and timeof the asset's linear broadcast distribution and can be used todetermine the on-line distribution date of the source video asset. Thecontent rights can include pricing and/or promotion of the distributionof the source video asset.

The non-linear planning subsystem generates a partner content avails andgenerates a metadata file of the source video asset that includes anupdated metadata field related to distribution of the source videoasset. The metadata files can be many types of files including wordprocessing documents, spreadsheet files, text files, HTML files, XMLfiles, and other files. The partner content avails generated by theplanning subsystem identifies a video asset and distribution time and/ordistribution territory and/or version (e.g., HD, foreign language, etc.)of the video asset. The planning system can automatically create apartner avails document based on partner content distribution dates,partner content rights, and the identified source video asset, and sendthe partner avails document to the distribution partners. The partneravails document can be sent to the distribution partners before theactual content.

The planning subsystem adds the source video asset to a playlist createdusing a planning user interface. The playlist feature of the planningsubsystem can scale upwards or downwards so that a single playlist ofsource video assets can be prepared and delivered to more than one ofthe distribution partners via a one-to-many model.

The system of the invention also includes a preparation subsystem suchas a non-linear asset preparation subsystem that creates a distributionpartner metadata file and/or an image file representing the source videoasset. The distribution partner metadata can include metadatacharacterizing many aspects of the source video asset, including a titleof the source video asset, a description of the source video asset, adate and time of recording of the source video asset, a broadcastnetwork to be recorded, a keyword related to the source video asset, aright of the distribution partner in the source video asset, platformcompatibility of the source video asset, an activation date of thesource video asset, a deactivation date of the source video asset, andother attributes.

The system of the invention also includes a transcoding subsystem, suchas a non-linear asset transcoding subsystem that receives the sourcevideo asset from the preparation system, schedules transcoding of thesource video asset, and transcodes the source video asset based upon adelivery date schedule. The transcoding schedule can be based on anumber of items including a native frame rate of the source video asset,a cadence correction error rate in the source video asset, a time ofday, a video codec, and other considerations. The transcoding caninclude creating closed caption files for the transcoded video asset,and the closed captions for the transcoded video asset can be timed tomatch the transcoded video file.

The system of the invention also includes a quality control subsystem,such as a non-linear asset quality control subsystem that examines thequality of the transcoded video asset, including native frame rates of atranscoded source video asset, lossy compression approximations of thetranscoded video asset, audio encoding that accompanies the transcodedvideo asset, and other qualities of the transcoded video asset. Thequality control subsystem can alert an operator when a quality controlmeasure requires intervention or when an error requires correction.

The system of the invention also includes a delivery subsystem, such asa delivery subsystem that receives a transcoded source video asset, ametadata file, and a representative image related to the transcodedvideo asset and assembles the asset, the metadata file, and image into adistributable video asset. The metadata files can be many types of filesincluding word processing documents, spreadsheet files, text files, HTMLfiles, XML files, and others. The delivery subsystem also deliversancillary materials with the video asset such as music cue sheets,extended metadata, extended images, and other ancillary materials alongwith the distributable video asset. The delivered (distributable) videoasset matches up with the partner avails document that was sent to thedistribution partner(s). More than one distribution partner may bedistributing the video asset, and individual partner avails documentscan be sent to each of the distribution partners for their distributionwith the video asset. The distributable video asset(s) and the partneravails document(s) of the distribution partner(s) can include matchingnonlinear asset identifiers to match up the specific partner availsdocument to the video asset.

The system of the invention can also include a workflow tracking servicethat identifies, tracks, and records states of the source video asset asthe source video asset moves through the system.

BRIEF DESCRIPTION OF THE DRAWINGS

The patent or application file contains at least one drawing executed incolor. Copies of this patent or patent application publication withcolor drawing(s) will be provided by the Office upon request and paymentof the necessary fee.

FIG. 1A shows a non-linear planning, preparation, and distributionsystem in accordance with the invention.

FIG. 1B shows a suite of application modules that provide the respectiveplanning, preparation, transcoding, quality assurance, and deliveryfunctionality of the invention.

FIG. 2 shows a media asset management subsystem components,applications, and services that carry out non-linear planning processesof the invention.

FIG. 3 shows a swim lane diagram of a non-linear planning, preparation,and delivery process of the invention.

FIG. 4 shows a persona diagram of a non-linear planning, preparation,and delivery processes of the invention.

FIGS. 5A-5B show a process flow of a non-linear, planning, preparation,and delivery process of the invention.

FIGS. 6A-6F are example user interface screens showing a manner in whicha non-linear planning, preparation, and delivery system of the inventionoperates on media content.

DETAILED DESCRIPTION

Previous generations of systems are limited in that they allow thescheduling and delivery of content, but do not include the planningprocess (which, in turn, feeds the downstream workflows). The inventionintegrates planning workflows into an orchestrated and efficient overalldistribution of the video assets and related materials such as metadata,images, closed caption files, music cue sheets, and other distributionmaterials.

FIG. 1A shows an operational and business overview of the non-linearvideo asset delivery ecosystem 199 of the invention. The planningportion (hardware and software) of the system resides in the planner,prep, and delivery system 110. The non-linear video asset deliveryecosystem 199 manages media assets to allow for the timely delivery ofcontent. Often, the cable television broadcasts are encoded anddelivered to the various distributors (Apple, Google, Microsoft, etc.)and are listed for sale the next day.

FIG. 1B shows a suite of application modules that provide the respectiveplanning, preparation, transcoding, quality assurance, and deliveryfunctionality of the planner, prep, and delivery system 110. Forexample, while FIG. 1A shows the relationship of the planner,preparation, and delivery system 110 to the overall non-linear videoasset delivery ecosystem 199, FIG. 1B breaks the functions of the system110 into respective apps and modules, including planning app 1300, prepapp 1354, transcode app 1355, quality control (QC) app 1361, anddelivery app 1371.

As detailed further below, the planning app receives a linear broadcastschedule 1302, content and metadata from content and metadata library1304, contract and rights information 1306, and brand priorities 1308and works in conjunction with distribution partner service 1120 for usein planning the delivery of content, taking into accountpartner-specific requirements. In the planning app 1300, the system 110chooses distribution partners, chooses content, schedules the contentlaunch, and tracks the content.

The prep app 1354 also works in conjunction with distribution partnerservice 1120 to choose images and add distribution values to theprepared content. Transcode app 1355 receives the source video asset,schedules the transcoding, and transcodes the source video asset. Thequality control (QC) app 1361 ensures that the system provides a qualitytranscoded asset, subject to partner-specific requirements. The deliveryapp 1371 works in conjunction with the partner service 1120 to scheduledelivery of the assets, track readiness, track deliver, and troubleshootdelivery problems of the assets, taking into account U.S. lineardeliveries 1382, U.S. syndicated content deliveries 1383, internationalsyndicated deliveries 1384, international program sales 1385,international joint ventures 1386, and international linear deliveries1387.

As shown in FIG. 2, the planner, prep, and delivery system 110 includesthe components, applications, and services that carry out the planningprocess described in the diagrams of FIGS. 3-5. FIG. 2 illustrates thehardware and technical components used to instantiate the sources, apps,and distribution endpoints shown in FIG. 1B. Framework 205 and planninguser interface 210 form the presentation layer and the business logicfor the planning system and process. Framework 205 can include aJavaScript framework such as Angular JS, Angular s, Angular 2, ReactJS,Vue.js, Vue 2.0, Ember.js, Meteor.js, and the like. Framework 205 andplanning user interface 210 provide end user facing features.

Planning service 215 supports the planning user interface 210 byreceiving instructional calls and messages to be processed. Based on themessage, via an application programming interface (API), the planningservice responds with actions such as a database entry or databaseretrieval. Planning database (dB) 220 can be a cloud-based database thatstores the content identifiers activation/deactivation dates, assetmetadata, and discrete sets of metadata for each distribution partner.

Cloud storage 225 includes a cloud-based storage device (e.g., memory,hard drive, server farm, etc.) such as a public cloud-based storagedevice for customized databases to support the planning process and togenerate reports. Media asset search (MAS) 230 provides a search indexof the assets (e.g., video, documents, files, and the like) by way ofmetadata, images, and/or asset type.

Message queue 235 includes a queue service that stores messages (datatransported between the sender application and the receiver application)as the messages travel between applications or services in the system.The message queue includes a sequence of work objects that are waitingto be processed. Data warehouse/reporting database 240 is a repositoryof data used to create analytics. The data stored in datawarehouse/reporting database 240 is used to discover, interpret, andcommunicate patterns in the data and is stored and accessed viareporting server 260.

Extract transform and load (ETL) tool 245 provides processes fordatabase usage and warehousing where data is extracted from homogeneousor heterogeneous data sources, transformed for storing in the properformat or structure for querying and analysis, and loaded into thetarget database. The tool 245 runs when moving raw data from its sourceto the data warehouse/dB 240.

Work flow tracking service 250 identifies and tracks the state of anasset in the workflow from the planning stage through the preparationstage to quality control and delivery stages. The service 250 tracks thelifecycle of the asset from planning, prep, and delivery. Other servicesin the system 110 can deposit and/or retrieve the asset status from thisservice. Workflow tracking database 255 stores the tracked asset statesfor retrieval and distribution by the service 250.

FIGS. 3-6 outline a non-linear planner, preparation, and deliveryprocess performed by the system 110 of the claimed invention to providevideo content to non-linear platforms and/or over the top (OTT) videoservices.

The process starts when a distribution partner, such as a subscriptionvideo-on-demand partner 120 (see FIG. 1), electronic sell-throughpartner 122, advertising video-on-demand partner 124, out of homevideo-on-demand partner 126, and the like, is entitled to content fromthe content provider 101. The relationship between the content provider101 and the distribution partners 120, 122, 124, 126 typically exists asa contractual commitment, where the content provider 101 provides videoassets to the distribution partners 120, 122, 124, 126, with stipulatedasset titles, quantities, formats, timing, video related images, contentmetadata and technical metadata, volumes of assets delivered per timeunit (i.e. week or month), and other specifications that may becontractually required of the video asset provider by the distributionpartners.

FIGS. 3-6 illustrate the non-linear planning, preparation, and deliveryprocess performed by the planner, prep, and delivery system 110 in FIGS.1A-1B. FIGS. 3-5 show like actions with like reference numerals. In FIG.3, the content planning application 300 directs the system to performnonlinear content distribution planning in block 301. A content provider101 selects content by searching for video assets (i.e., content) andplacing the video assets in a distribution “partner” playlist 600 asshown further in the example planning user interface screen of FIG. 6A.As detailed further in the persona diagram of FIG. 4 and the flow chartof FIG. 5, in block 505, the programming team sets up a playlist 600 inwhich the video asset(s) 602 will reside in cloud database 220 bysearching and identifying a particular asset based upon title 604,content, host, actor, time, linear premiere date 606, marketingcommitments, and new platform launches 608. The planning service 215searches and identifies the video asset 602 by metadata tags of thevideo asset. Once the planning service 215 identifies the asset 602, theplanning service 215 receives the show art in block 510. In block 515,the system determines pricing and promotions for the video asset. As theplanning process moves forward, the planner, prep, and delivery system110 modifies the files of the video asset, including the video file (viatranscoding), the image file (via resizing), and the metadata (via XSLTXML transformation to include the updated fields (e.g., show art,pricing and promotion, marketing priority tags, activation anddeactivation dates, and other fields. Once the attributes of the video,XML, and image files are associated and linked to the video asset, inblock 520, the system joins the video asset to the playlist 600. Upondetermining whether additional assets will be added to the playlist inblock 525, the system 110 continues to add assets by returning to block505 until the playlist 602 is complete. Once the playlist 600 iscomplete, the playlist 600 resides in the collection of playlists asshown in FIG. 6B.

In blocks 330 and 530, respectively, the planner, prep, and deliverysystem 110 determines and displays a linear broadcast schedule (airdate) and aligns the online activation date 608 accordingly. That is,the on-line video assets may not be available to viewers from thedistribution partners 120, 122, 124, 126 simultaneously on the broadcastdate. For example, some online assets are available immediately afterthe broadcast schedule airdate and can be purchased by viewers at thattime. Likewise, other online assets or other versions of the same onlineasset can be viewed, via Pay-TV authentication, starting the next-day.During the first three (3) days after the original broadcast airdate,the content includes the full advertising load (i.e., C3 content).Similarly, other versions of the online asset can be accessed by viewersfour days or after from the broadcast schedule airdate (i.e., D4+content) with a reduced ad load via dynamic ad insertion (DAI).

In blocks 335 and 535 respectively, the system checks the distributionpartners and platform, the content itself, and other partner-related andcontent-related rights to make sure that content has the outbound rightsfor that platform. The rights can be different for different versions ofthe same underlying asset. In blocks 340 and 540, respectively, thesystem 110 then automates and generates the partner avails document,which the system sends in blocks 345 and 545 to the partner before theactual content is delivered. Sending the partner avails documentidentifies an asset and confirms the partner distribution strategy forthe asset. The partner avails document includes business informationregarding the availability of the offered assets and providesinformation about the time, location, and business rules related to theoffered asset. For example, the avails document can include informationfor standard-definition (SD) and high-definition (HD) versions, forvideo-on-demand (VOD) and electronic sell-through (EST) licenses, forthe availability of the content in different territories, and the like.At the same time, the system forwards the asset to the preparationsubsystem in block 550 and to the transcoding subsystem in block 555.

Following the flow diagram path from block 550 in FIG. 5A to referenceblock 1 in FIG. 5B, once the planning operations are complete, thesystem 110 prepares the assets in block 354 (in FIG. 3) where thepartner metadata is prepared in block 358 and block 558, respectively.The system prepares the partner metadata by editing and updatingmetadata specific to that partner. For example, as also shown in FIG.6C, the system edits, updates, and embeds metadata related to the titles620 and descriptions, dates and times of the recording, of the broadcastnetwork to be recorded, keywords, rights in the asset, platformcompatibility, activation and deactivation dates 624, 626 for thedistribution partner to honor, and other video asset information for aspecific partner site 628. Often the partners have to adhere to custommetadata specifications as part of the video asset provider-distributionpartner contract. By editing, updating, and embedding the partnermetadata, contextual information regarding the video asset can beascertained, cataloged, indexed, and retrieved.

As part of the video asset preparation, the system preps the image 632in blocks 362 and 562, respectively. The image prep subsystem selects animage 632 (from image selections 634) that best represents that video onthat specific partner site. The image prep can be an image grab from thevideo asset itself or can be another visual representation indicative ofthat video on that partner site. Once the system 110 completes thepartner metadata prep 558 and the image prep 562, the system forwardsthe metadata, images, and other video asset attributes to the deliverysubsystem in block 564.

Meanwhile, in parallel to the partner metadata prep 558 and the imageprep 562, the system 110 forwards the video asset to the transcodingsubsystem and initiates a transcoding request in block 355 and block555, respectively. Following the flow diagram path from block 555 inFIG. 5A to reference block 2 in FIG. 5B, the system 110 receives thesource video asset and schedules transcoding of the source video asset602 in block 557. As also shown in the transcoding system user interfaceexample of FIG. 6D, the scheduling of the transcoding can be based onthe delivery due dates 642 of the assets 602. Based on a threshold ofdata, such as native frame rate of the source video asset or the cadencecorrection error rate in the source video asset provided on the asset,the system will transcode the source video asset 602 in block 559. Thetranscoding can include converting the asset from one video codec formto another. For example, a program can be broadcast at one resolutionand can be provided to a partner site at a different resolution. Thesystem 110 normalizes the load on the transcoding subsystems byefficiently moving non-urgent content to be transcoded during off peakhours (such as nights and weekends).

Once the video asset is transcoded, the system performs quality controlmeasures in block 361 and 561, respectively. For example, in block 363,the quality control subsystem confirms that the transcoding is not toolossy. FIG. 6E shows a detailed user interface for the quality controloperations. The quality control subsystem also examines native framerates, identifies and corrects audio issues, and alerts system operatorswhen the transcoded asset requires additional intervention. The systemcan take quality control measures more quickly than in the past, as thevideo assets are moving in parallel through the prep and transcodingsubsystems.

Depending upon the type of quality problem evident in the transcodedvideo asset 602, some video assets may require re-ingestion, that is,recapturing, transferring, or importing the video asset file into thetranscoding subsystem. Other video assets may require logging ofadditional descriptive comments to provide additional information tovideo asset provider personnel who will handle the asset in the future.Other video assets may require re-transcoding to produce a new set ofrenditions, frame settings, timings, while still others may requirere-ingestion of captions or other video overlay materials. Once thesystem completes the quality control measures, the transcoded videoasset is forwarded to the delivery subsystem in block 365 and block 565,respectively, where it meets up with the forwarded metadata, images, andother video asset attributes from the preparation subsystem.

In block 367 and block 567, respectively, the system 110 identifies andassembles artifacts. For example, the system assembles the metadata andrepresentative image from the prep subsystem and the video file andcaptioning information from the transcoding and quality controlsubsystems, as well as encryption files and other artifacts. The system110 tracks artifacts and monitors the state of each of the artifactsthrough the subsystems with the reporting server 260. The system 110stores the states of the artifacts in the data warehouse/reportingdatabase 240 for subsequent analysis. Once the system 110 identifies theartifact (component) of the video asset as technically sound and ready,the system 110 green-lights that artifact (component). The system 110verifies a video asset launch date/time and verifies that the partneravails have been sent to the distribution partner 120, 122, 124, 126.When the system 110 green lights all the artifacts (components) in block569, the asset is ready for delivery.

In block 571, the delivery subsystem delivers the XML or JSON files(e.g., the partner avails document and the prepped partner metadata,etc.), the image from the prep subsystem, and the transcoded andquality-assured video file to the distribution partners 120, 122, 124,126 for distribution over multiple platforms. As further shown in thedelivery user interface of FIG. 6F, the system 110 can also includeadditional ancillary materials that accompany the video asset, such asclosed captions, music queue sheets, recipes, timing sheets, and thelike. While the system can deliver the video asset to the distributionpartners 120, 122, 124, 126 as soon as the system green lights all theartifacts, the system can also schedule delivery to the distributionpartners so the asset is not delivered too early or too late to thepartner. The system can track the due date 664 for delivery to thedistribution partners 120, 122, 124, 126 and the delivery date 662. Thesystem optimizes the delivery date based on the date of the assetactivation on the partner site. Similarly, the system can scheduledelivery of the video asset during times of reduced network traffic orduring times of reduced cost network transfers. Once the system deliversthe content to the partner, a nonlinear asset ID 666 is used toassociate the content to the asset metadata, which was delivered to thepartner via the avails document. The avails document is typically sentprior to the arrival of the video content.

The non-linear program planner, preparation, and delivery systemperforms multiplatform planning and scheduling for content beingdelivered to multiple content delivery platforms. The system coordinatesend-to-end planning to deliver high-quality video content in a veryefficient and scalable manner. The system includes automated partnercontent avails and other processes that increases the accuracy of theinformation provided to distribution partners. The system checks oncontent rights and incorporates metadata structures that facilitatedelivery of content to a wide range of distribution channels. Theinvention increases accuracy, timeliness, and efficiency of contentdelivered to partners and allows providers to generate revenue fromonline (non-linear) platforms and over the top (OTT) video services.

We claim:
 1. A system for non-linear video asset program planning,preparation, and delivery, the system comprising: a processor forexecuting applications stored in a non-transitory computer-readablemedium, the applications comprising: a non-linear planning subsystemapplication that receives a linear broadcast schedule from a linearschedule service application, receives content rights from a contentrights application, and receives a source video asset from a storagedevice, and the non-linear planning application generates a partnercontent avails and generates a metadata file of the source video assetthat includes an updated metadata field related to distribution of thesource video asset and adds the source video asset to a playlist createdusing a planning user interface, and wherein the non-linear planningapplication automatically creates a partner avails document based onpartner content distribution dates, partner content rights, and thesource video asset, and sends the partner avails document todistribution partners.
 2. A system of claim 1, wherein the metadata fileis at least one of a word processing document, a spreadsheet file, atext file, an HTML file, and an XML file.
 3. A system of claim 1,wherein the linear broadcast schedule determines an on-line distributiondate of the source video asset.
 4. A system of claim 1, wherein thecontent rights include at least one of pricing and promotion ofdistribution of the source video asset.
 5. A system of claim 1, whereinthe playlist of source video assets created using the planning userinterface scales for preparation and delivery of the playlist to aplurality of video content distribution partners via a one to manymodel.
 6. A system of claim 1, wherein the partner content availsidentifies a source video asset and at least one of time of non-lineardistribution of the source video asset, territory of distribution of thesource video asset, and version of the source video asset.
 7. A systemof claim 1 further comprising: a non-linear asset preparation subsystemserver that creates at least one of distribution partner metadata fileand an image file representing the source video asset.
 8. A system ofclaim 7, wherein the distribution partner metadata the includes metadatacharacterizing at least one of a title of the source video asset, adescription of the source video asset, a date and time of recording ofthe source video asset, a broadcast network to be recorded, a keywordrelated to the source video asset, rights of the distribution partnersin the source video asset, platform compatibility of the source videoasset, an activation date of the source video asset, and a deactivationdate of the source video asset.
 9. A system of claim 1 furthercomprising: a non-linear asset transcoding application that receives thesource video asset from a preparation subsystem server, schedulestranscoding of the source video asset, and transcodes the source videoasset based upon a delivery date schedule.
 10. A system of claim 9,wherein the non-linear asset transcoding application transcodes thesource video asset based upon at least one of a native frame rate of thesource video asset, a cadence correction error rate in the source videoasset, a time of day, and a video codec.
 11. A system of claim 9,wherein the non-linear asset transcoding application creates closedcaption files for the transcoded video asset.
 12. A system of claim 11,wherein the closed caption files for the transcoded video asset aretimed to match the transcoded video asset.
 13. A system of claim 1further comprising: a non-linear asset quality control application thatexamines at least one of native frame rates of a transcoded source videoasset, lossy compression approximations of the transcoded video asset,and audio encoding that accompanies the transcoded video asset.
 14. Asystem of claim 13, wherein the non-linear asset quality controlapplication alerts a system operator when an error requires correction.15. A system of claim 1 further comprising: a delivery application thatreceives a transcoded source video asset, a metadata file, and arepresentative image related to the transcoded source video asset andassembles the transcoded source video asset, the metadata file, and therepresentative image into a distributable video asset.
 16. A system ofclaim 15, wherein the delivery application assembles and delivers atleast one of music cue sheets, extended metadata, and extended imageswith the distributable video asset.
 17. A system of claim 15, whereinthe distributable video asset corresponds to a delivered partner availsdocument of a distribution partner.
 18. A system of claim 17, whereinthe distributable video asset and the partner avails document of thedistribution partner include a matching nonlinear asset identifier. 19.A system of claim 1 further comprising: a work flow tracking servicethat identifies, tracks, and records states of the source video asset asthe source video asset moves through the system.
 20. A system of claim 1further comprising: a work flow tracking service that identifies andtracks a state and lifecycle of the source video asset as the sourcevideo asset proceeds through the system.